-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a CONTRIBUTING.md #30
Conversation
for more information, see https://pre-commit.ci
Probably the most exciting PR you've seen (in your lives?). Related to fun I was having over in - UCL-ARC/coding-standards#30
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
For the merge strategy, I'd enforce that through the repo settings, don't think that needs to go in the CONTIBUTING.md
necessarily.
Co-authored-by: Milan Malfait <38256462+milanmlft@users.noreply.github.com>
I agree with this |
My question was rather:
What do you want me to do here. Shall I change it? Shall we have a rule that auto merges upon approval of one if no comments? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good
(squashing FTW - enforced in settings)
<!-- prettier-ignore --> | ||
> [!NOTE] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will mean only the [!NOTE]
is not formatted. The rest will be (which is the bit that isn't broken).
[GitHub flavoured markdown]: | ||
https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is valid syntax, so no need to ignore prettier
here either
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Automerging should be used with great caution |
based on UCL-ARC/python-tooling.
@paddyroddy strong opinion about the merging strategy?